Assert nullable executions in parametrized tests with special approach #290
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
EgorkaKulikov
force-pushed
the
egor/deep-equals-parametrized
branch
from
4a0fb03 to
c6e644b
Compare
Damtev
approved these changes
Jun 23, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Use
asserNullif expected result is null. Use standard deepEquals assertion otherwise.Create "deepEqualsWrapper" to select between this two options
Fixes # (252)
Type of Change
Please delete options that are not relevant.
How Has This Been Tested?
Automated Testing
CastExample.simpleCastfromutbot-samplesManual Scenario
Check that different parametrized tests do not crash with
NullPointerException.